Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accelerator 4] Updating configuration and accelerators to support APIM 4.4 and IS 7.0 #129

Merged
merged 7 commits into from
Oct 11, 2024

Conversation

Ashi1993
Copy link
Contributor

@Ashi1993 Ashi1993 commented Oct 2, 2024

Updating configuration and accelerators to support APIM 4.4 and IS 7.0

Explain in a few lines the purpose of this pull request

Issue link: required

Doc Issue: Optional, link issue from documentation repository

Applicable Labels: Spec, product, version, type (specify requested labels)


Development Checklist

  1. Build complete solution with pull request in place.
  2. Ran checkstyle plugin with pull request in place.
  3. Ran Findbugs plugin with pull request in place.
  4. Ran FindSecurityBugs plugin and verified report.
  5. Formatted code according to WSO2 code style.
  6. Have you verified the PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?
  7. Migration scripts written (if applicable).
  8. Have you followed secure coding standards in WSO2 Secure Engineering Guidelines?

Testing Checklist

  1. Written unit tests.
  2. Verified tests in multiple database environments (if applicable).
  3. Tested with BI enabled (if applicable).

pom.xml Show resolved Hide resolved
@Akila94 Akila94 merged commit a580405 into wso2:main Oct 11, 2024
2 checks passed
@Ashi1993 Ashi1993 changed the title Updating configuration and accelerators to support APIM 4.4 and IS 7.0 [Accelerator 4] Updating configuration and accelerators to support APIM 4.4 and IS 7.0 Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants